Update DistTasks.yml #168
Merged
Update DistTasks.yml #168
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
During my investigations I discovered this typo which was causing a problem: ``` mkdir: cannot create directory ‘serial-monitor_linux_arm_6’: File exists task: Failed to run task "dist:all": task: Failed to run task "dist:Linux_ARM64": exit status 1 ```
per1234
approved these changes
Sep 21, 2021
|
Thanks @umbynos! I see this typo has propagated to every project we used the taskfile in. However, I believe it is innocuous in the other projects since the If so, we don't need to worry about there being problems with the artifacts produced by the releases that used the previous version of the taskfile in those projects. Am I right about that? |
per1234
added
topic: code
|
That's correct. I stumbled upon this problem because I tried to create the dir this way before running the |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During my investigations I discovered this typo which was causing a problem: